Recommending configurations for client networking environment based on aggregated cloud managed information

ABSTRACT

Disclosed are systems, methods, and computer-readable storage media for recommending configurations for a client networking environment based on aggregated cloud managed information. A cloud network management device can receive a first set of infrastructure specifications describing a first client networking environment. The cloud network management device can determine a set of recommended configurations for the first client networking environment based on the first set of infrastructure specifications and configurations for one or more client networking environments determined to be similar to the first client networking environment. The cloud network management device can provide the set of recommended configurations to a client device associated with the first client networking environment.

TECHNICAL FIELD

This disclosure relates in general to the field of computer networksand, more particularly, pertains to recommending configurations for aclient networking environment based on aggregated cloud managedinformation.

BACKGROUND

Modern computer networking environments can be configured for a specificorganization's needs. For example, configurations such as securitysettings, firewall settings, blacklists, etc., can be tailored based onthe type of organization (e.g., education retail, government, etc.),type of hardware, number of devices, etc. Currently, systemadministrators are tasked with manually setting and adjustingconfigurations for their computer networking environments. In additionto being both labor intensive and time consuming, a system administratoris also limited to their individual judgment and personal experiencewhen selecting configuration settings. Accordingly, improvements areneeded.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited features andother advantages of the disclosure can be obtained, a more particulardescription of the principles briefly described above will be renderedby reference to specific embodiments thereof which are illustrated inthe appended drawings. Understanding that these drawings depict onlyexemplary embodiments of the disclosure and are not therefore to beconsidered to be limiting its scope, the principles herein are describedand explained with additional specificity and detail through the use ofthe accompanying drawings in which:

FIG. 1 illustrates an example network device according to some aspectsof the subject technology;

FIGS. 2A and 2B illustrate an example system embodiments according tosome aspects of the subject technology;

FIG. 3 illustrates a schematic block diagram of an example architecturefor a network fabric;

FIG. 4 illustrates an example overlay network;

FIG. 5 illustrates an example system for recommending configurations fora client networking environment based on aggregated cloud managedinformation;

FIG. 6 illustrates an example system embodiment of a cloud managementdevice for recommending configurations for a client networkingenvironment based on aggregated cloud managed information; and

FIG. 7 illustrates an example method of recommending configurations fora client networking environment based on aggregated cloud managedinformation.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The detailed description set forth below is intended as a description ofvarious configurations of the subject technology and is not intended torepresent the only configurations in which the subject technology can bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a more thoroughunderstanding of the subject technology. However, it will be clear andapparent that the subject technology is not limited to the specificdetails set forth herein and may be practiced without these details. Insome instances, structures and components are shown in block diagramform in order to avoid obscuring the concepts of the subject technology.

Overview

Disclosed are systems, methods, and computer-readable storage media forrecommending configurations for a client networking environment based onaggregated cloud managed information. A cloud network management devicecan receive a first set of infrastructure specifications describing afirst client networking environment. The cloud network management devicecan determine a set of recommended configurations for the first clientnetworking environment based on the first set of infrastructurespecifications and configurations for one or more client networkingenvironments determined to be similar to the first client networkingenvironment. The cloud network management device can provide the set ofrecommended configurations to a client device associated with the firstclient networking environment.

Detailed Description

Disclosed are systems and methods for recommending configurations for aclient networking environment based on aggregated cloud managedinformation. A brief introductory description of exemplary systems andnetworks, as illustrated in FIGS. 1 through 4, is disclosed herein,followed by a discussion of recommending configurations for a clientnetworking environment based on aggregated cloud managed information.The disclosure now turns to FIG. 1.

A computer network is a geographically distributed collection of nodesinterconnected by communication links and segments for transporting databetween endpoints, such as personal computers and workstations. Manytypes of networks are available, with the types ranging from local areanetworks (LANs) and wide area networks (WANs) to overlay andsoftware-defined networks, such as virtual extensible local areanetworks (VXLANs).

LANs typically connect nodes over dedicated private communications linkslocated in the same general physical location, such as a building orcampus. WANs, on the other hand, typically connect geographicallydispersed nodes over long-distance communications links, such as commoncarrier telephone lines, optical lightpaths, synchronous opticalnetworks (SONET), or synchronous digital hierarchy (SDH) links. LANs andWANs can include layer 2 (L2) and/or layer 3 (L3) networks and devices.

The Internet is an example of a WAN that connects disparate networksthroughout the world, providing global communication between nodes onvarious networks. The nodes typically communicate over the network byexchanging discrete frames or packets of data according to predefinedprotocols, such as the Transmission Control Protocol/Internet Protocol(TCP/IP). In this context, a protocol can refer to a set of rulesdefining how the nodes interact with each other. Computer networks maybe further interconnected by an intermediate network node, such as arouter, to extend the effective “size” of each network.

Overlay networks generally allow virtual networks to be created andlayered over a physical network infrastructure. Overlay networkprotocols, such as Virtual Extensible LAN (VXLAN), NetworkVirtualization using Generic Routing Encapsulation (NVGRE), NetworkVirtualization Overlays (NVO3), and Stateless Transport Tunneling (STT),provide a traffic encapsulation scheme which allows network traffic tobe carried across L2 and L3 networks over a logical tunnel. Such logicaltunnels can be originated and terminated through virtual tunnel endpoints (VTEPs).

Moreover, overlay networks can include virtual segments, such as VXLANsegments in a VXLAN overlay network, which can include virtual L2 and/orL3 overlay networks over which virtual machines (VMs) communicate. Thevirtual segments can be identified through a virtual network identifier(VNI), such as a VXLAN network identifier, which can specificallyidentify an associated virtual segment or domain.

Network virtualization allows hardware and software resources to becombined in a virtual network. For example, network virtualization canallow multiple numbers of VMs to be attached to the physical network viarespective virtual LANs (VLANs). The VMs can be grouped according totheir respective VLAN, and can communicate with other VMs as well asother devices on the internal or external network.

Network segments, such as physical or virtual segments; networks;devices; ports; physical or logical links; and/or traffic in general canbe grouped into a bridge or flood domain. A bridge domain or flooddomain can represent a broadcast domain, such as an L2 broadcast domain.A bridge domain or flood domain can include a single subnet, but canalso include multiple subnets. Moreover, a bridge domain can beassociated with a bridge domain interface on a network device, such as aswitch. A bridge domain interface can be a logical interface whichsupports traffic between an L2 bridged network and an L3 routed network.In addition, a bridge domain interface can support internet protocol(IP) termination, VPN termination, address resolution handling, MACaddressing, etc. Both bridge domains and bridge domain interfaces can beidentified by a same index or identifier.

Furthermore, endpoint groups (EPGs) can be used in a network for mappingapplications to the network. In particular, EPGs can use a grouping ofapplication endpoints in a network to apply connectivity and policy tothe group of applications. EPGs can act as a container for buckets orcollections of applications, or application components, and tiers forimplementing forwarding and policy logic. EPGs also allow separation ofnetwork policy, security, and forwarding from addressing by insteadusing logical application boundaries.

Cloud computing can also be provided in one or more networks to providecomputing services using shared resources. Cloud computing can generallyinclude Internet-based computing in which computing resources aredynamically provisioned and allocated to client or user computers orother devices on-demand, from a collection of resources available viathe network (e.g., “the cloud”). Cloud computing resources, for example,can include any type of resource, such as computing, storage, andnetwork devices, virtual machines (VMs), etc. For instance, resourcesmay include service devices (firewalls, deep packet inspectors, trafficmonitors, load balancers, etc.), compute/processing devices (servers,CPU's, memory, brute force processing capability), storage devices(e.g., network attached storages, storage area network devices), etc. Inaddition, such resources may be used to support virtual networks,virtual machines (VM), databases, applications (Apps), etc.

Cloud computing resources may include a “private cloud,” a “publiccloud,” and/or a “hybrid cloud.” A “hybrid cloud” can be a cloudinfrastructure composed of two or more clouds that inter-operate orfederate through technology. In essence, a hybrid cloud is aninteraction between private and public clouds where a private cloudjoins a public cloud and utilizes public cloud resources in a secure andscalable manner. Cloud computing resources can also be provisioned viavirtual networks in an overlay network, such as a VXLAN.

FIG. 1 illustrates an exemplary network device 110 suitable forimplementing the present technology. Network device 110 includes amaster central processing unit (CPU) 162, interfaces 168, and a bus 115(e.g., a PCI bus). When acting under the control of appropriate softwareor firmware, the CPU 162 is responsible for executing packet management,error detection, and/or routing functions, such policy enforcement, forexample. The CPU 162 preferably accomplishes all these functions underthe control of software including an operating system and anyappropriate applications software. CPU 162 may include one or moreprocessors 163 such as a processor from the Motorola family ofmicroprocessors or the MIPS family of microprocessors. In an alternativeembodiment, processor 163 is specially designed hardware for controllingthe operations of router 110. In a specific embodiment, a memory 161(such as non-volatile RAM and/or ROM) also forms part of CPU 162.However, there are many different ways in which memory could be coupledto the system.

The interfaces 168 are typically provided as interface cards (sometimesreferred to as “line cards”). Generally, they control the sending andreceiving of data packets over the network and sometimes support otherperipherals used with the network device 110. Among the interfaces thatmay be provided are Ethernet interfaces, frame relay interfaces, cableinterfaces, DSL interfaces, token ring interfaces, and the like. Inaddition, various very high-speed interfaces may be provided such asfast token ring interfaces, wireless interfaces, Ethernet interfaces,Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POSinterfaces, FDDI interfaces and the like. Generally, these interfacesmay include ports appropriate for communication with the appropriatemedia. In some cases, they may also include an independent processorand, in some instances, volatile RAM. The independent processors maycontrol such communications intensive tasks as packet switching, mediacontrol, and management. By providing separate processors for thecommunications intensive tasks, these interfaces allow the mastermicroprocessor 162 to efficiently perform routing computations, networkdiagnostics, security functions, etc.

Although the system shown in FIG. 1 is one specific network device ofthe present technology, it is by no means the only network devicearchitecture on which the present technology can be implemented. Forexample, an architecture having a single processor that handlescommunications as well as routing computations, etc. is often used.Further, other types of interfaces and media could also be used with therouter.

Regardless of the network device's configuration, it may employ one ormore memories or memory modules (including memory 161) configured tostore program instructions for the general-purpose network operationsand mechanisms for roaming, route optimization and routing functionsdescribed herein. The program instructions may control the operation ofan operating system and/or one or more applications, for example. Thememory or memories may also be configured to store tables such asmobility binding, registration, and association tables, etc.

FIG. 2A, and FIG. 2B illustrate exemplary possible system embodiments.The more appropriate embodiment will be apparent to those of ordinaryskill in the art when practicing the present technology. Persons ofordinary skill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 2A illustrates a conventional system bus computing systemarchitecture 200 wherein the components of the system are in electricalcommunication with each other using a bus 205. Exemplary system 200includes a processing unit (CPU or processor) 210 and a system bus 205that couples various system components including the system memory 215,such as read only memory (ROM) 220 and random access memory (RAM) 225,to the processor 210. The system 200 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 210. The system 200 can copy data from the memory215 and/or the storage device 230 to the cache 212 for quick access bythe processor 210. In this way, the cache can provide a performanceboost that avoids processor 210 delays while waiting for data. These andother modules can control or be configured to control the processor 210to perform various actions. Other system memory 215 may be available foruse as well. The memory 215 can include multiple different types ofmemory with different performance characteristics. The processor 210 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 232, module 2 234, and module 3 236 stored instorage device 230, configured to control the processor 210 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 210 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 200, an inputdevice 245 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 235 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 200. The communications interface240 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 230 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 225, read only memory (ROM) 220, andhybrids thereof.

The storage device 230 can include software modules 232, 234, 236 forcontrolling the processor 210. Other hardware or software modules arecontemplated. The storage device 230 can be connected to the system bus205. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 210, bus 205, display 235, and soforth, to carry out the function.

FIG. 2B illustrates a computer system 250 having a chipset architecturethat can be used in executing the described method and generating anddisplaying a graphical user interface (GUI). Computer system 250 is anexample of computer hardware, software, and firmware that can be used toimplement the disclosed technology. System 250 can include a processor255, representative of any number of physically and/or logicallydistinct resources capable of executing software, firmware, and hardwareconfigured to perform identified computations. Processor 255 cancommunicate with a chipset 260 that can control input to and output fromprocessor 255. In this example, chipset 260 outputs information tooutput 265, such as a display, and can read and write information tostorage device 270, which can include magnetic media, and solid statemedia, for example. Chipset 260 can also read data from and write datato RAM 275. A bridge 280 for interfacing with a variety of userinterface components 285 can be provided for interfacing with chipset260. Such user interface components 285 can include a keyboard, amicrophone, touch detection and processing circuitry, a pointing device,such as a mouse, and so on. In general, inputs to system 250 can comefrom any of a variety of sources, machine generated and/or humangenerated.

Chipset 260 can also interface with one or more communication interfaces290 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 255 analyzing data stored in storage 270 or 275.Further, the machine can receive inputs from a user via user interfacecomponents 285 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 255.

It can be appreciated that exemplary systems 200 and 250 can have morethan one processor 210 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

FIG. 3 illustrates a schematic block diagram of an example architecture300 for a network fabric 312. The network fabric 312 can include spineswitches 302 _(A), 302 _(B), . . . , 302 _(N) (collectively “302”)connected to leaf switches 304 _(A), 304 _(B), 304 _(C) . . . 304 _(N)(collectively “304”) in the network fabric 312.

Spine switches 302 can be L3 switches in the fabric 312. However, insome cases, the spine switches 302 can also, or otherwise, perform L2functionalities. Further, the spine switches 302 can support variouscapabilities, such as 40 or 10 Gbps Ethernet speeds. To this end, thespine switches 302 can include one or more 40 Gigabit Ethernet ports.Each port can also be split to support other speeds. For example, a 40Gigabit Ethernet port can be split into four 10 Gigabit Ethernet ports.

In some embodiments, one or more of the spine switches 302 can beconfigured to host a proxy function that performs a lookup of theendpoint address identifier to locator mapping in a mapping database onbehalf of leaf switches 304 that do not have such mapping. The proxyfunction can do this by parsing through the packet to the encapsulatedtenant packet to get to the destination locator address of the tenant.The spine switches 302 can then perform a lookup of their local mappingdatabase to determine the correct locator address of the packet andforward the packet to the locator address without changing certainfields in the header of the packet.

When a packet is received at a spine switch 302 _(i), the spine switch302 _(i) can first check if the destination locator address is a proxyaddress. If so, the spine switch 302 _(i) can perform the proxy functionas previously mentioned. If not, the spine switch 302 _(i) can look upthe locator in its forwarding table and forward the packet accordingly.

Spine switches 302 connect to leaf switches 304 in the fabric 312. Leafswitches 304 can include access ports (or non-fabric ports) and fabricports. Fabric ports can provide uplinks to the spine switches 302, whileaccess ports can provide connectivity for devices, hosts, endpoints,VMs, or external networks to the fabric 312.

Leaf switches 304 can reside at the edge of the fabric 312, and can thusrepresent the physical network edge. In some cases, the leaf switches304 can be top-of-rack (“ToR”) switches configured according to a ToRarchitecture. In other cases, the leaf switches 304 can be aggregationswitches in any particular topology, such as end-of-row (EoR) ormiddle-of-row (MoR) topologies. The leaf switches 304 can also representaggregation switches, for example.

The leaf switches 304 can be responsible for routing and/or bridging thetenant packets and applying network policies. In some cases, a leafswitch can perform one or more additional functions, such asimplementing a mapping cache, sending packets to the proxy function whenthere is a miss in the cache, encapsulate packets, enforce ingress oregress policies, etc.

Moreover, the leaf switches 304 can contain virtual switchingfunctionalities, such as a virtual tunnel endpoint (VTEP) function asexplained below in the discussion of VTEP 408 in FIG. 4. To this end,leaf switches 304 can connect the fabric 312 to an overlay network, suchas overlay network 400 illustrated in FIG. 4.

Network connectivity in the fabric 312 can flow through the leafswitches 304. Here, the leaf switches 304 can provide servers,resources, endpoints, external networks, or VMs access to the fabric312, and can connect the leaf switches 304 to each other. In some cases,the leaf switches 304 can connect EPGs to the fabric 312 and/or anyexternal networks. Each EPG can connect to the fabric 312 via one of theleaf switches 304, for example.

Endpoints 310A-E (collectively “310”) can connect to the fabric 312 vialeaf switches 304. For example, endpoints 310A and 310B can connectdirectly to leaf switch 304A, which can connect endpoints 310A and 310Bto the fabric 312 and/or any other one of the leaf switches 304.Similarly, endpoint 310E can connect directly to leaf switch 304C, whichcan connect endpoint 310E to the fabric 312 and/or any other of the leafswitches 304. On the other hand, endpoints 310C and 310D can connect toleaf switch 304B via L2 network 306. Similarly, the wide area network(WAN) can connect to the leaf switches 304C or 304D via L3 network 308.

Endpoints 310 can include any communication device, such as a computer,a server, a switch, a router, etc. In some cases, the endpoints 310 caninclude a server, hypervisor, or switch configured with a VTEPfunctionality which connects an overlay network, such as overlay network400 below, with the fabric 312. For example, in some cases, theendpoints 310 can represent one or more of the VTEPs 408A-D illustratedin FIG. 4. Here, the VTEPs 408A-D can connect to the fabric 312 via theleaf switches 304. The overlay network can host physical devices, suchas servers, applications, EPGs, virtual segments, virtual workloads,etc. In addition, the endpoints 310 can host virtual workload(s),clusters, and applications or services, which can connect with thefabric 312 or any other device or network, including an externalnetwork. For example, one or more endpoints 310 can host, or connect to,a cluster of load balancers or an EPG of various applications.

Although the fabric 312 is illustrated and described herein as anexample leaf-spine architecture, one of ordinary skill in the art willreadily recognize that the subject technology can be implemented basedon any network fabric, including any data center or cloud networkfabric. Indeed, other architectures, designs, infrastructures, andvariations are contemplated herein.

FIG. 4 illustrates an exemplary overlay network 400. Overlay network 400uses an overlay protocol, such as VXLAN, VGRE, VO3, or STT, toencapsulate traffic in L2 and/or L3 packets which can cross overlay L3boundaries in the network. As illustrated in FIG. 4, overlay network 400can include hosts 406A-D interconnected via network 402.

Network 402 can include a packet network, such as an IP network, forexample. Moreover, network 402 can connect the overlay network 400 withthe fabric 312 in FIG. 3. For example, VTEPs 408A-D can connect with theleaf switches 304 in the fabric 312 via network 402.

Hosts 406A-D include virtual tunnel end points (VTEP) 408A-D, which canbe virtual nodes or switches configured to encapsulate andde-encapsulate data traffic according to a specific overlay protocol ofthe network 400, for the various virtual network identifiers (VNIDs)410A-I. Moreover, hosts 406A-D can include servers containing a VTEPfunctionality, hypervisors, and physical switches, such as L3 switches,configured with a VTEP functionality. For example, hosts 406A and 406Bcan be physical switches configured to run VTEPs 408A-B. Here, hosts406A and 406B can be connected to servers 404A-D, which, in some cases,can include virtual workloads through VMs loaded on the servers, forexample.

In some embodiments, network 400 can be a VXLAN network, and VTEPs408A-D can be VXLAN tunnel end points (VTEP). However, as one ofordinary skill in the art will readily recognize, network 400 canrepresent any type of overlay or software-defined network, such asNVGRE, STT, or even overlay technologies yet to be invented.

The VNIDs can represent the segregated virtual networks in overlaynetwork 400. Each of the overlay tunnels (VTEPs 408A-D) can include oneor more VNIDs. For example, VTEP 408A can include VNIDs 1 and 2, VTEP408B can include VNIDs 1 and 2, VTEP 408C can include VNIDs 1 and 2, andVTEP 408D can include VNIDs 1-3. As one of ordinary skill in the artwill readily recognize, any particular VTEP can, in other embodiments,have numerous VNIDs, including more than the 3 VNIDs illustrated in FIG.4.

The traffic in overlay network 400 can be segregated logically accordingto specific VNIDs. This way, traffic intended for VNID 1 can be accessedby devices residing in VNID 1, while other devices residing in otherVNIDs (e.g., VNIDs 2 and 3) can be prevented from accessing suchtraffic. In other words, devices or endpoints connected to specificVNIDs can communicate with other devices or endpoints connected to thesame specific VNIDs, while traffic from separate VNIDs can be isolatedto prevent devices or endpoints in other specific VNIDs from accessingtraffic in different VNIDs.

Servers 404A-D and VMs 404E-I can connect to their respective VNID orvirtual segment, and communicate with other servers or VMs residing inthe same VNID or virtual segment. For example, server 404A cancommunicate with server 404C and VMs 404E and 404G because they allreside in the same VNID, viz., VNID 1. Similarly, server 404B cancommunicate with VMs 404F and 404H because they all reside in VNID 2.VMs 404E-1 can host virtual workloads, which can include applicationworkloads, resources, and services, for example. However, in some cases,servers 404A-D can similarly host virtual workloads through VMs hostedon the servers 404A-D. Moreover, each of the servers 404A-D and VMs404E-I can represent a single server or VM, but can also representmultiple servers or VMs, such as a cluster of servers or VMs.

VTEPs 408A-D can encapsulate packets directed at the various VNIDs 1-3in the overlay network 400 according to the specific overlay protocolimplemented, such as VXLAN, so traffic can be properly transmitted tothe correct VNID and recipient(s). Moreover, when a switch, router, orother network device receives a packet to be transmitted to a recipientin the overlay network 400, it can analyze a routing table, such as alookup table, to determine where such packet needs to be transmitted sothe traffic reaches the appropriate recipient. For example, if VTEP 408Areceives a packet from endpoint 404B that is intended for endpoint 404H,VTEP 408A can analyze a routing table that maps the intended endpoint,endpoint 404H, to a specific switch that is configured to handlecommunications intended for endpoint 404H. VTEP 408A might not initiallyknow, when it receives the packet from endpoint 404B, that such packetshould be transmitted to VTEP 408D in order to reach endpoint 404H.Accordingly, by analyzing the routing table, VTEP 408A can lookupendpoint 404H, which is the intended recipient, and determine that thepacket should be transmitted to VTEP 408D, as specified in the routingtable based on endpoint-to-switch mappings or bindings, so the packetcan be transmitted to, and received by, endpoint 404H as expected.

However, continuing with the previous example, in many instances, VTEP408A may analyze the routing table and fail to find any bindings ormappings associated with the intended recipient, e.g., endpoint 404H.Here, the routing table may not yet have learned routing informationregarding endpoint 404H. In this scenario, the VTEP 408A may likelybroadcast or multicast the packet to ensure the proper switch associatedwith endpoint 404H can receive the packet and further route it toendpoint 404H.

In some cases, the routing table can be dynamically and continuouslymodified by removing unnecessary or stale entries and adding new ornecessary entries, in order to maintain the routing table up-to-date,accurate, and efficient, while reducing or limiting the size of thetable.

As one of ordinary skill in the art will readily recognize, the examplesand technologies provided above are simply for clarity and explanationpurposes, and can include many additional concepts and variations.

Depending on the desired implementation in the network 400, a variety ofnetworking and messaging protocols may be used, including but notlimited to TCP/IP, open systems interconnection (OSI), file transferprotocol (FTP), universal plug and play (UpnP), network file system(NFS), common internet file system (CIFS), AppleTalk etc. As would beappreciated by those skilled in the art, the network 400 illustrated inFIG. 4 is used for purposes of explanation, a network system may beimplemented with many variations, as appropriate, in the configurationof network platform in accordance with various embodiments of thepresent disclosure.

Having disclosed a brief introductory description of exemplary systemsand networks, the discussion now turns to recommending configurationsfor a client networking environment based on aggregated cloud managedinformation. A cloud management system can allow users to manage clientnetworking environments. For example, the cloud management system canprovide users with a management interface that allows users to setconfigurations, such as security settings, firewall settings,whitelists, blacklists, etc., for their respective client networkingenvironment. The cloud management system can communicate with computingnodes in client networking environments to implement any receivedconfigurations.

In addition to enabling users to easily manage their client networkingenvironments, the cloud management system can also analyze aggregateddata to provide users with recommended configurations for their clientnetworking environments. For example, the cloud networking managementsystem can determine a set of recommended configurations for a clientnetworking environment based on configurations for other clientnetworking environments that are determined to be similar. To accomplishthis, the cloud management system can cluster client networkingenvironments into environment similarity groups such that eachenvironment similarity group includes client networking environmentsdetermined to be similar to each other based on infrastructurespecifications describing the cloud networking environments. The cloudmanagement system can analyze configuration data for the clientnetworking environments in an environment similarity group to determinecommonly selected configurations for the environment similarity group.The cloud management system can then use the commonly selectedconfigurations to provide a set of recommendation configurations tousers managing similar client networking environments.

FIG. 5 illustrates an example system 500 for recommending configurationsfor a client networking environment based on aggregated cloud managedinformation. As shown, system 500 includes cloud management system 502,client devices 504 ₁, 504 ₂ . . . 504 _(n) (collectively “504”), andclient networking environments 506 ₁, 506 ₂, . . . 506 _(n)(collectively “506”). Cloud management system 502 can be a cloud basedcomputing system that allows users to remotely manage their clientnetworking environments. A client networking environment can includemultiple computing nodes, such as firewalls, servers, routers, accesspoints, etc.

Cloud management system 502 can provide users with a managementinterface that allows users to set configurations, such as securitysettings, firewall settings, whitelists, blacklists, etc., for theirrespective client networking environment. Users (e.g., systemadministrators) can use client devices 504 to communicate with cloudmanagement system 502 to access the management interface and set oradjust configurations. Cloud management system 502 can communicate withcomputing nodes in client networking environments to implement anyreceived configurations.

In addition to enabling users to easily manage their client networkingenvironments 504, cloud management system 502 can also analyzeaggregated data to provide users with recommended configurations fortheir client networking environments 504. For example, cloud managementsystem 502 can identify common configurations for client networkingenvironments determined to be similar to each other and use the commonconfigurations to provide a set of recommended configurations to userswith other similar client networking environments. Examples ofrecommended configurations can include URL categories, malwaredefinitions, etc.

Cloud management system 502 can maintain infrastructure specificationsand configuration data for multiple client networking environments.Infrastructure specifications can include any type of data describing aclient networking environment, such as data describing the types ofcomputing devices, number of users, number of devices, field (e.g,education, retail, government, etc.), geographic location, etc.Configuration data can include any configurations set for a clientnetworking environment, such as security settings, firewall settings,category blocking, white lists, black lists, etc. Cloud managementsystem 502 can receive the infrastructure specifications andconfiguration data from clients utilizing cloud management system 502 tomanage their client networking environments. Further cloud managementsystem 502 can receive infrastructure specifications and configurationdata from 3^(rd) party vendors (not shown).

Cloud management system 502 can aggregate and analyze the infrastructurespecifications to identify client networking environments that aresimilar to each other. For example, cloud management system 502 cancluster client networking environments into environment similaritygroups based on the infrastructure specifications describing the cloudnetworking environments such that each environment similarity groupincludes client networking environments determined to be similar to eachother. Cloud management system 502 can cluster the client networkingenvironments using any known clustering method or algorithm, such as ak-means clustering algorithm.

As another example, cloud management system 502 can infer a customervertical for client networking environments and assign client networkingenvironments in the same customer vertical into an environmentsimilarity group. To infer a customer vertical, cloud management system502 can use data from 3rd party vendors, such as Salesforce, Zoom Info,Boomerang, etc., as data inputs. This 3^(rd) part data can be combinedwith additional information (e.g., features) related to a clientnetworking environment maintained by cloud management system 502. Cloudmanagement system 502 can then use this data along with supervisedcategorization techniques, such as multilevel logical regression andrandom forest, to accurately infer the customer vertical.

Cloud management system 502 can analyze configuration data for theclient networking environments in an environment similarity group todetermine commonly selected configurations for the environmentsimilarity group. Cloud management system 502 can then use the commonlyselected configurations for an environment similarity group to provide aset of recommendation configurations to users managing other similarclient networking environments.

FIG. 6 illustrates an example system embodiment of a cloud managementdevice 600 for recommending configurations for a client networkingenvironment based on aggregated cloud managed information. A cloudmanagement system can include any number cloud management devices. Asshown, cloud management device 600 includes management interface module602, clustering module 604, recommendation module 606 and data storage608. Management interface module 602 can be configured to provide a userwith a management interface that enables a user to set configurationsfor a client networking environment. The management interface caninclude user interface elements (e.g., text fields, buttons, etc.) thatenable the user to set configurations for the client networkingenvironment and/or individual computing nodes in the client networkingenvironment. Management interface module 602 can store receivedconfigurations for a client networking environment in data storage 608.Management interface module 602 can further be configured to communicatewith a client networking environment to implement configurations set byan administrator.

Clustering module 604 can be configured to cluster client networkingenvironments into environment similarity groups. Data storage 608 canstore infrastructure specifications describing client networkingenvironments as well as corresponding configuration data. Clusteringmodule 604 can communicate with data storage 608 to gather theinfrastructure specifications and cluster the client networkingenvironments based on the infrastructure specifications. For example,clustering module 604 can use a known clustering algorithm such as ak-means clustering algorithm. Clustering module 604 can store datadefining the resulting environment similarity groups in data storage608.

Recommendation module 606 can be configured to determine a set ofrecommended configurations for a client networking environment based onthe environment similarity groups. Recommendation module 606 can receiveinfrastructure specifications describing a client networkingenvironment, for example as a result of a new client establishing aclient networking environment.

In some embodiments, recommendation module 606 can provide theinfrastructure specifications to clustering module 604, which can assignthe client networking environment to an environment similarity group andprovide data identifying the environment similarity group torecommendation module 606. Recommendation module 606 can communicatewith data storage 608 to gather configuration data for client networkingenvironments in the environment similarity group to determine a set ofcommonly selected configurations for client networking environments inthe environment similarity group. Recommendation module 606 can use theset of commonly selected configurations to provide a set of recommendedconfigurations. For example, recommendation module 606 can provide theset of recommended configurations to management interface module 602,which can present the set of recommended configurations to a user. Forexample, the set of recommended configurations can be pre-populated fora user to either approve or alter.

In some embodiments, recommendation module 606 can determine a set ofrecommended configurations without use of clustering module 604. Forexample, recommendation module 606 can analyze infrastructurespecifications in data storage 608 to identify a set of one or moreclient networking environments that are similar or that share similarcharacteristics to a client networking environment. Recommendationmodule 606 can determine a set of recommended configurations for theclient networking environment based on the configurations for theidentified set of client networking environments that are similar orthat share similar characteristics. For example, recommendation module606 can search analyze infrastructure specifications to identify clientnetworking environments that have a similar size, similar number ofcomputing devices, are in a similar geographic location and/or share asimilar customer vertical.

FIG. 7 illustrates an example method of recommending configurations fora client networking environment based on aggregated cloud managedinformation. It should be understood that there can be additional,fewer, or alternative steps performed in similar or alternative orders,or in parallel, within the scope of the various embodiments unlessotherwise stated.

At step 702, a cloud management device can receive a first set ofinfrastructure specifications describing a first client networkingenvironment. The infrastructure specifications can include at least oneof types of computing devices, number of users, number of devices, fieldor geographic location.

At step 704, the cloud management device can determine a set ofrecommended configurations for the first client networking environmentbased on the first set of infrastructure specifications andconfigurations for one or more client networking environments determinedto be similar to the first client networking environment. The cloudmanagement device can receiving infrastructure specifications andconfigurations for a plurality of client networking environments, whichincludes the one or more client networking environments determined to besimilar to the first client networking environment. In some embodiments,the cloud management device can determine the similar computing devicesby identifying, based on the infrastructure specifications for theplurality of client networking environments, client networkingenvironments that include infrastructure specifications that are similarto the first client networking environment.

In some embodiments, the cloud management device can determine thesimilar computing devices by clustering the plurality of clientnetworking environments into a plurality of environment similaritygroups based on the infrastructure specifications for the plurality ofclient networking environments such that each environment similaritygroup includes client networking environments determined to be similarto each other. For example, the clustering can be performed using ak-means clustering algorithm. The cloud management device can thendetermine, based on first set of infrastructure specifications, thatclient networking environments in a first environment similarity groupare similar to the first client networking environment. The cloudmanagement device can then determine the set of recommendedconfigurations for the first client networking environment based onconfigurations for the client networking environments in the firstenvironment similarity group.

At step 706, the cloud management device can provide the set ofrecommended configurations to a client device associated with the firstclient networking environment. For example, the set of recommendedconfiguration can be presented in a management interface.

As one of ordinary skill in the art will readily recognize, the examplesand technologies provided above are simply for clarity and explanationpurposes, and can include many additional concepts and variations.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, rackmount devices, standalone devices, and so on.Functionality described herein also can be embodied in peripherals oradd-in cards. Such functionality can also be implemented on a circuitboard among different chips or different processes executing in a singledevice, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims. Moreover, claimlanguage reciting “at least one of” a set indicates that one member ofthe set or multiple members of the set satisfy the claim.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Note that in certain example implementations, the optimization and/orplacement functions outlined herein may be implemented by logic encodedin one or more tangible, non-transitory media (e.g., embedded logicprovided in an application specific integrated circuit [ASIC], digitalsignal processor [DSP] instructions, software [potentially inclusive ofobject code and source code] to be executed by a processor, or othersimilar machine, etc.). The computer-readable storage devices, mediums,and memories can include a cable or wireless signal containing a bitstream and the like. However, when mentioned, non-transitorycomputer-readable storage media expressly exclude media such as energy,carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

The invention claimed is:
 1. A method comprising: receiving, by a cloudmanagement device, a first set of infrastructure specificationsdescribing a first client networking environment; determining, by thecloud management device, a set of recommended configurations for thefirst client networking environment, comprising: identifying, based onthe first set of infrastructure specifications, a group of clientnetworking environments; and selecting, as the set of recommendedconfigurations, configurations that are common to the group of clientnetwork environments; providing, by the cloud management device, the setof recommended configurations to a client device associated with thefirst client networking environment; implementing the set of recommendedconfigurations on the client device; wherein the infrastructurespecifications includes types of computing devices, number of users,number of devices, field and geographic location, and wherein the groupof client networking environments is created using a k-means clusteringalgorithm.
 2. A cloud management system comprising: one or more computerprocessors; and a memory storing instructions that, when executed by theone or more computer processors, cause the cloud management system to:receive a first set of infrastructure specifications describing a firstclient networking environment; determine a set of recommendedconfigurations for the first client networking environment, comprising:identify, based on the first set of infrastructure specifications agroup of client networking environments; and select, as the set ofrecommended configurations, configurations that are common to the groupof client network environments; provide the set of recommendedconfigurations to a client device associated with the first clientnetworking environment; implement the set of recommended configurationson the client device; wherein the infrastructure specifications includestypes of computing devices, number of users, number of devices, fieldand geographic location, and wherein clustering the plurality of clientnetworking environments is performed using a k-means clusteringalgorithm.
 3. A non-transitory computer-readable medium storinginstructions that, when executed by a cloud management device, cause thecloud management device to: receive a first set of infrastructurespecifications describing a first client networking environment;determine a set of recommended configurations for the first clientnetworking environment, comprising: identify, based on the first set ofinfrastructure specifications a group of client networking environments;and select, as the set of recommended configurations, configurationsthat are common to the group of client network environments; provide theset of recommended configurations to a client device associated with thefirst client networking environment; implementing the set of recommendedconfigurations on the client device; wherein the infrastructurespecifications includes types of computing devices, number of users,number of devices, field and geographic location, and wherein the groupof client networking environments is created using a k-means clusteringalgorithm.